This page last changed on Dec 14, 2004 by plightbo.
- XWork upgraded to 1.0.5
- Using i18n, especially the ww:text tag, is now possible in SiteMesh decorators. See SiteMesh.
- Issues where the ActionContext wasn't properly cleaned up (after ww:include and ww:action) have been resolved.
- Configuration
- If the action class is not specified, it now defaults to com.opensymphony.xwork.ActionSupport.
- If the result name is not specified, it is assumed to be "success".
- Non-UI tags
- ww:text and ww:url have an id attribute that, when specified, causes the tag not to print out the localized text but rather store the result in the ActionContext to be referenced later. See SiteMesh, URL tag, and Text Tag.
- UI tags
- ww:form has an added target attribute.
- ww:form exposes "namespace" in the parameters Map in templates.
- ww:form tag defaults the id and name attribute to the action name that it is submitting to.
- Form elements default the id attribute to "[formId]_[elementName]".
- Form elements default the "required" attribute to true if there is any validator associated with that field and the form's validate attribute is enabled.
- ww:textarea has an added "wrap" attribute.
- XHTML theme: added a parameter called "after" and that will add text to the right of the form element.
- Replaced old prototype client-side validation with XmlHttpRequest-based solution (STILL IN PROTOTYPE PHASE, works in XHTML theme only).
- Interceptors
- ServletConfigInterceptor now checks for actions implementing PrincipalAware and adds a Principal that ties in to the HttpServletRequest's Principal.
- Minor bug fixes in the ExecuteAndWaitInterceptor and FileUploadInterceptor.
- Results
- JasperReportsResult and StreamResult both support the Content-disposition header.
- JasperReports integration has been upgraded to 0.6.3.
- WebWorkResultSupport has a simple conditionalParse() method making support for ${} notation in your results easier (it will parse only if the parse attribute is true).
- Copy over the new webwork.jar and xwork.jar files.
- If you are using JasperReports, you will need to upgrade to the latest JasperReports jars of 0.6.3 because the package name has changed.
- Read the migration notes for anything that you should be aware of.
- If you were using the old client-side validation code, it is still possible to keep using it but you will likely need to modify form-close.vm and controlheader.vm in the XHTML theme and form.vm in the simple theme. We recommend supporting the new prototype as it is a lot easier to use and doesn't require special validators.
- It is possible, though very unlikely, that the default ids for the UI tags and the default name for the form tag might cause you some trouble. Please be aware of this change.
|